home *** CD-ROM | disk | FTP | other *** search
- I have been thinking about the issue of supporting international character
- sets in IMAP2bis better than they presently are. Although IMAP2bis goes a
- great way towards internationalization with its MIME support, there are some
- gaps, most notably SEARCH.
-
- I believe that modifying SEARCH is generally a show-stopper for IMAP2bis; it's
- too complex an issue to address at this go-round. It'll open a whole can of
- worms including pent-up demands for new features and will prevent the rest of
- IMAP2bis from being finalized for a long time.
-
- However, I am considering one possibility to assist our foreign friends. That
- is, to define that search strings are now in the proposed format used to
- express multinational characters in message headers. I forget the exact RFC
- number, but it came out as a companion to MIME. Since message headers have to
- be 7-bit US-ASCII forever because of the needs of header parsers, a means was
- invented by the MIME group to encode international characters in strings such
- as personal names.
-
- I believe that if we define that the search strings use this format for
- specifying multinational characters, it will not introduce an incompatability.
- The worst thing that would happen is that you would get a false negative when
- searching for texts in the message body if the IMAP server does not support
- that character set. You would get a true positive with a current IMAP server
- for international characters in the header!
-
- Due to the characteristics of the strings in question, I feel that a false
- positive is unlikely and certainly much less likely than ignoring 8th bits or
- ISO-2022 shifts.
-
- I would like to hear, particularly from my friends at NTT, if this would be
- helpful. I think it is better than the current choices: no multinational
- search, or coercion the string into 7-bit ASCII and lots of false positives.
-
- Implementation of this proposal is another matter! ;-)
-
- -- Mark --
-
-